home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
8_7_11.tro
< prev
next >
Wrap
Text File
|
1991-12-22
|
69KB
|
2,689 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright (~c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v'|.5i'
.LP
SECTION\ 3\ \(em\ MESSAGE TRANSFER AGENT ABSTRACT SERVICE
.sp 1P
.RT
.sp 2P
.LP
\fB10\fR \fBRefined message transfer system model\fR
.sp 1P
.RT
.PP
Paragraph 6 describes the MTS as an object, without reference to
its internal structure. This paragraph refines the MTS model, and exposes
its component objects and the ports shared between them.
.PP
Figure\ 3/X.411 models the MTS and reveals its internal structure.
.PP
The MTS comprises a collection of message\(hytransfer\(hyagent (MTA)
objects, which cooperate together to form the MTS and offer the MTS abstract
service to its users. It is the MTAs which perform the active functions
of the MTS,\ i.e. transfer of messages, probes and reports, generation
of reports, and content conversion.
.PP
MTA objects also have ports, some of which are precisely those which are
also visible at the boundary of the MTS object, i.e. submission\(hyports,
delivery\(hyports and administration ports. However, MTAs also have another
type of port\ \(em\ which are concerned with the distribution of the MTS
abstract service between the MTAs, and are not visible at the boundary
of the MTS object.
.PP
A transfer\(hyport enables an MTA to transfer messages, probes and
reports to another MTA. In general, a message, probe or report may have
to be transferred a number of times between different MTAs to reach its
intended
destination.
.PP
If a message is addressed to multiple recipients served by several
different MTAs, the message must be transferred through the MTS along several
different paths. From the perspective of an MTA transferring such a message,
some recipients may be reached via one path while other recipients may be
reached via another. At such an MTA, two copies of the message are created,
and each is transferred to the next MTA along its respective path. The
copying
and branching of the message is repeated until each copy has reached a final
destination\ MTA, where the message can be delivered to one or more recipient
MTS\(hyusers.
.PP
Every MTA along a path taken by a message is responsible for
delivering or transferring the message to a particular subset of the
originally\(hyspecified\(hyrecipients. Other MTAs take care of the deliver or
transfer to remaining recipients, using copies of the messages created along
the way.
.PP
Reports on the delivery or non\(hydelivery of a message to one or more
recipient MTS\(hyusers, are generated by MTAs in accordance with the request of
the originator of the message and the originating\(hyMTA. An MTA may generate a
delivery\(hyreport upon successfully delivering a copy of a message to
a recipient MTS\(hyuser. It may generate a non\(hydelivery\(hyreport upon
determining that a copy of a message is undeliverable to one or more recipients,
that is, it is unable to deliver the message to the recipient MTS\(hyusers,
or it is unable to transfer the message to an adjacent MTA that would take
responsibility for delivery or
transferring the message further.
.PP
For efficiency, an MTA may generate a single, combined report that
applies to several copies of a single, multiple recipient message for which
it is responsible. Both delivery\(hy and non\(hydelivery\(hyreports may
be combined
together. However, in order for reports to be combined in this manner,
the same content conversion, if any, must have been performed on the message
for all
recipients to whom the report refers.
.PP
Reports that pertain to copies of the same multiple recipient message but
that were generated by different MTAs are not combined by any intermediate
MTAs, but instead remain distinct.
.PP
When required, an MTA may perform content conversion. When neither
the originating nor the recipient MTS\(hyuser requests nor prohibits conversion,
implicit conversion of a message's encoded\(hyinformation\(hytypes may
be performed by an MTA to suit the encoded\(hyinformation\(hytypes that
the recipient MTS\(hyuser is able to receive. The originating MTS\(hyuser
may also explicitly request
conversion of specific encoded\(hyinformation\(hytypes for a particular
recipient
MTS\(hyuser.
.PP
The submission\(hy, delivery\(hy and administration\(hyports of an MTA,
which are also visible at the boundary of the MTS, are defined in Section\
2 of this Recommendation. The remaining paragraphs in this section define
the
transfer\(hyport of an MTA, and the procedures performed by MTAs to ensure the
correct distributed operation of the MTS.
.bp
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure 3/X.411, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB11\fR \fBMessage transfer agent abstract service overview\fR
.sp 1P
.RT
.PP
Section two defines the MTS abstract service provided by the
submission\(hy, delivery\(hy and administration\(hyports of an MTA. This
paragraph
defines the following abstract\(hyoperations that are provided by the
transfer\(hyports of MTAs:
.RT
.LP
\fIMTA\(hybind and MTA\(hyunbind\fR
.LP
a)
MTA\(hybind
.LP
b)
MTA\(hyunbind.
.LP
\fITransfer port abstract\(hyoperations\fR
.LP
c)
message\(hytransfer
.LP
d)
probe\(hytransfer
.LP
e)
report\(hytransfer.
.sp 1P
.LP
11.1
\fIMTA\(hybind and MTA\(hyunbind\fR
.sp 9p
.RT
.PP
The \fBMTA\(hybind\fR enables an MTA to establish an association with
another MTA. Abstract\(hyoperations other than MTA\(hybind can only be
invoked in the context of an established association.
.PP
The \fBMTA\(hyunbind\fR enables an MTA to establish an association with
another MTA. Abstract\(hyoperations other than MTA\(hybind can only be
invoked in the context of an established association.
.RT
.sp 1P
.LP
11.2
\fITransfer port abstract\(hyoperations\fR
.sp 9p
.RT
.PP
The \fBmessage\(hytransfer\fR abstract\(hyoperation enables an MTA to
transfer a message to another MTA.
.PP
The \fBprobe\(hytransfer\fR abstract\(hyoperation enables an MTA to transfer
a probe to another MTA.
.PP
The \fBreport\(hytransfer\fR abstract\(hyoperation enables an MTA to transfer
a report to another MTA.
.RT
.sp 2P
.LP
\fB12\fR \fBMessage transfer agent abstract service definition\fR
.sp 1P
.RT
.PP
The MTS abstract service is defined in\ \(sc\ 8. This paragraph defines the
semantics of the parameters of the abract\(hyservice provided by the transfer\(hyport
of MTAs.
.PP
Paragraph 12.1 defines the MTA\(hybind and MTA\(hyunbind. Paragraph 12.2
defines the transfer\(hyport. Paragraph\ 12.3 defines some common parameter
types.
.PP
The abstract\(hysyntax of the MTA abstract service is defined
in\ \(sc\ 13.
.bp
.RT
.sp 1P
.LP
12.1
\fIMTA\(hybind and MTA\(hyunbind\fR
.sp 9p
.RT
.PP
This paragraph defines the abstract\(hyservice used to establish and release
associations between MTAs.
.RT
.sp 1P
.LP
12.1.1
\fIAbstract\(hybind and abstract\(hyunbind\fR
.sp 9p
.RT
.PP
This paragraph defines the following abstract\(hybind and
abstract\(hyunbind:
.RT
.LP
a)
MTA\(hybind
.LP
b)
MTA\(hyunbind.
.sp 1P
.LP
12.1.1.1\ \ \fIMTA\(hybind\fR
.sp 9p
.RT
.PP
The MTA\(hybind enables an MTA to establish an association with
another MTA.
.PP
The MTA\(hybind establishes the \fBcredentials\fR of MTAs to interact, and
the \fBapplication\(hycontext\fR and \fBsecurity\(hycontext\fR of the association.
An
assocition can only be released by the initiator of that association (using
MTA\(hyunbind).
.PP
Abstract\(hyoperations other than MTA\(hybind can only be invoked in the
context of an established association.
.PP
The successful completion of the MTA\(hybind signifies the establishment
of an association.
.PP
The disruption of the MTA\(hybind by a bind\(hyerror indicates that an
association has not been established.
.RT
.sp 1P
.LP
12.1.1.1.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 27/X.411 lists the arguments of the MTA\(hybind, and for each
argument qualifies its presence and indicates the paragraph in which the
argument is defined.
.RT
.ce
\fBH.T. [T27.411]\fR
.ce
TABLE\ 27/X.411
.ce
\fBMTA\(hybind arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
\fIBind arguments\fR
.T&
lw(90p) | cw(30p) | cw(36p) .
Initiator\(hyname O 12.1.1.1.1.1
.T&
lw(90p) | cw(30p) | cw(36p) .
Initiator\(hycredentials O 12.1.1.1.1.2
.T&
lw(90p) | cw(30p) | cw(36p) .
Security\(hycontext O 12.1.1.1.1.3
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 27/X.411 [T27.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
12.1.1.1.1.1\ \ \fIInitiator\(hyname\fR
.sp 9p
.RT
.PP
This argument contains a name for the initiator of the association. It
may be generated by the initiator of the association.
.PP
The name of an \fBMTA\(hyname\fR .
.RT
.sp 1P
.LP
12.1.1.1.1.2\ \ \fIInitiator\(hycredentials\fR
.sp 9p
.RT
.PP
This argument contains the \fBcredentials\fR of the initiator of the
association. It may be generated by the initiator of the association.
.PP
The \fBinitiator\(hycredentials\fR may be used by the responder to
authenticate the identity of the initiator (see Recommendation\ X.509).
.PP
If only simple\(hyauthentication is proposed, the \fBinitiator\(hycredentials\fR
comprise a simple \fBpassword\fR associated with the \fBinitiator\(hyname\fR
.
.PP
If strong\(hyauthentication is used, the \fBinitiator\(hycredentials\fR
comprise an \fBinitiator\(hybind\(hytoken\fR and, optionally, an \fBinitiator\(hycertificate\fR
.
.bp
.PP
The \fBinitiator\(hybind\(hytoken\fR is a \fBtoken\fR generated by the
initiator of the association. If the \fBinitiator\(hybind\(hytoken\fR is
an \fBasymmetric\(hytoken\fR , the
\fBsigned\(hydata\fR comprises a \fBrandom\(hynumber\fR . The \fBencrypted\(hydata\fR
of an
\fBasymmetric\(hytoken\fR may be used to convey secret security\(hyrelevant
information (e.g.,\ one or more symmetric\(hyencryption\(hykeys) used to
secure the association, or may be absent from the \fBinitiator\(hybind\(hytoken\fR
.
.PP
The \fBinitiator\(hycertificate\fR is a \fBcertificate\fR of the initiator
of the association, generated by a trusted source (e.g.,\ a certification\(hyauthority).
It may be supplied by the initiator of the association, if the
\fBinitiator\(hybind\(hytoken\fR is an \fBasymmetric\(hytoken\fR . The
\fBinitiator\(hycertificate\fR may be used to convey a verified copy of
the public\(hyasymmetric\(hyencryption\(hykey (\fBsubject\(hykey\fR ) of
the initiator of the association. The initiator's
public\(hyasymmetric\(hyencryption\(hykey may be used by the responder
to compute the
\fBresponder\(hybind\(hytoken\fR . If the responder is known to have, or
have access to, the initiator's certificate (e.g.,\ via the Directory),
the
\fBinitiator\(hycertificate\fR may be omitted.
.RT
.sp 1P
.LP
12.1.1.1.1.3\ \ \fISecurity\(hycontext\fR
.sp 9p
.RT
.PP
This argument indicates the \fBsecurity\(hycontext\fR that the initiator
of the association proposes to operate at. It may be generated by the initiator
of the association.
.PP
The \fBsecurity\(hycontext\fR comprises one or more \fBsecurity\(hylabels\fR
that
defines the sensitivity of interactions that may occur between the MTAs
for the duration of the association, in line with the security\(hypolicy
in force. The
\fBsecurity\(hycontext\fR shall be one that is allowed by the \fBsecurity\(hylabels\fR
associated with the MDs (MTAs).
.PP
If \fBsecurity\(hycontexts\fR are not established between the MTAs, the
sensitivity of interactions that may occur between the MTAs may be at the
discretion of the invoker of an abstract\(hyoperation.
.RT
.sp 1P
.LP
12.1.1.1.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
Table\ 28/X.411 lists the results of the MTA\(hybind, and for each
result qualifies its presence and indicates the paragraph in which the
result is defined.
.RT
.ce
\fBH.T. [T28.411]\fR
.ce
TABLE\ 28/X.411
.ce
\fBMTA\(hybind results
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Result Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
\fIBind results\fR
.T&
lw(90p) | cw(30p) | cw(36p) .
Responder\(hyname O 12.1.1.1.2.1
.T&
lw(90p) | cw(30p) | cw(36p) .
Responder\(hycredentials O 12.1.1.1.2.2
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 28/X.411 [T28.411], p. \fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
12.1.1.1.2.1\ \ \fIResponder\(hyname\fR
.sp 9p
.RT
.PP
This argument contains a name for the responder of the association. It
may be generated by the responder of the association.
.PP
The name is an \fBMTA\(hyname\fR .
.RT
.sp 1P
.LP
12.1.1.1.2.2\ \ \fIResponder\(hycredentials\fR
.sp 9p
.RT
.PP
This argument contains the \fBcredentials\fR of the responder of the
association. It may be generated by the responder of the association.
.PP
The \fBresponder\(hycredentials\fR may be used by the initiator to
authenticate the identity of the responder (see Recommendation\ X.509).
.PP
If only simple\(hyauthentication is used, the \fBresponder\(hycredentials\fR
comprise a simple \fBpassword\fR associated with the \fBresponder\(hyname\fR .
.bp
.PP
If strong\(hyauthentication is used, the \fBresponder\(hycredentials\fR
comprise a \fBresponder\(hybind\(hytoken\fR . The \fBresponder\(hybind\(hytoken\fR
is a \fBtoken\fR generated by the responder of the association. The \fBresponder\(hybind\(hytoken\fR
shall be the same type of \fBtoken\fR as the \fBinitiator\(hybind\(hytoken\fR
. If the \fBresponder\(hybind\(hytoken\fR is an \fBasymmetric\(hytoken\fR
, the \fBsigned\(hydata\fR comprises a \fBrandom\(hynumber\fR (which may
be related to the \fBrandom\(hynumber\fR supplied in the \fBinitiator\(hybind\(hytoken\fR
). The \fBencrypted\(hydata\fR of an \fBasymmetric\(hytoken\fR may be used
to convey
security\(hyrelevant information (e.g.,\ one or more symmetric\(hyencryption\(hykeys)
used to secure the association, or may be absent from the
\fBresponder\(hybind\(hytoken\fR .
.RT
.sp 1P
.LP
12.1.1.1.3\ \ \fIBind\(hyerrors\fR
.sp 9p
.RT
.PP
The bind\(hyerrors that may disrupt the MTA\(hybind are defined
in\ \(sc\ 12.1.2.
.RT
.sp 1P
.LP
12.1.1.2\ \ \fIMTA\(hyunbind\fR
.sp 9p
.RT
.PP
The MTA\(hyunbind enables the release of an established association by
the initiator of the association.
.RT
.sp 1P
.LP
12.1.1.2.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
The MTA\(hyunbind service has no arguments.
.RT
.sp 1P
.LP
12.1.1.2.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The MTA\(hyunbind service returns an empty result as indication of
release of the association.
.RT
.sp 1P
.LP
12.1.1.2.3\ \ \fIUnbind\(hyerrors\fR
.sp 9p
.RT
.PP
There are no unbind\(hyerrors that may disrupt the MTA\(hyunbind.
.RT
.sp 1P
.LP
12.1.2
\fIBind\(hyerrors\fR
.sp 9p
.RT
.PP
This paragraph defines the following bind\(hyerrors:
.RT
.LP
a)
authentication\(hyerror,
.LP
b)
busy,
.LP
c)
unacceptable\(hydialogue\(hymode,
.LP
d)
unacceptable\(hysecurity\(hycontext.
.sp 1P
.LP
12.1.2.1\ \ \fIAuthentication\(hyerror\fR
.sp 9p
.RT
.PP
The authentication\(hyerror bind\(hyerror reports that an association
cannot be established due to an authentication error; the initiator's
\fBcredentials\fR are not acceptable or are improperly specified.
.PP
The authentication\(hyerror bind\(hyerror has no parameters.
.RT
.sp 1P
.LP
12.1.2.2\ \ \fIBusy\fR
.sp 9p
.RT
.PP
The busy bind\(hyerror reports that an association cannot be
established because the responder is busy.
.PP
The busy bind\(hyerror has no parameters.
.RT
.sp 1P
.LP
12.1.2.3\ \ \fIUnacceptable\(hydialogue\(hymode\fR
.sp 9p
.RT
.PP
The unacceptable\(hydialogue\(hymode bind\(hyerror reports that the
dialogue\(hymode proposed by the initiator of the association is unacceptable
to the responder (see\ \(sc\ 12 of Recommendation\ X.419).
.PP
The unacceptable\(hydialogue\(hymode bind\(hyerror has no parameters.
.RT
.sp 1P
.LP
12.1.2.4\ \ \fIUnacceptable\(hysecurity\(hycontext\fR
.sp 9p
.RT
.PP
The unacceptable\(hysecurity\(hycontext\(hybind\(hyerror reports that the
\fBsecurity\(hycontext\fR proposed by the initiator of the association
is unacceptable to the responder.
.PP
The Unacceptable\(hysecurity\(hycontext bind\(hyerror has no parameters.
.bp
.RT
.sp 1P
.LP
12.2
\fITransfer port\fR
.sp 9p
.RT
.PP
This paragraph defines the abstract\(hyoperations and abstract\(hyerrors
which occur at a transfer\(hyport.
.RT
.sp 1P
.LP
12.2.1
\fIAbstract\(hyoperations\fR
.sp 9p
.RT
.PP
This paragraph defines the following transfer\(hyport
abstract\(hyoperations:
.RT
.LP
a)
message\(hytransfer,
.LP
b)
probe\(hytransfer,
.LP
c)
report\(hytransfer.
.sp 1P
.LP
12.2.1.1\ \ \fIMessage\(hytransfer\fR
.sp 9p
.RT
.PP
The message\(hytransfer abstract\(hyoperation enables the MTA to transfer
a message to another MTA.
.RT
.sp 1P
.LP
12.2.1.1.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 29/X.411 lists the arguments of the message\(hytransfer
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the paragraph in which the argument is defined.
.RT
.sp 1P
.LP
12.2.1.1.1.1\ \ \fIMessage\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains an \fBMTS\(hyidentifier\fR that distinguishes the
message from all other messages, probes and reports within the MTS. It
shall be generated by the originating\(hyMTA of the message, and shall
have the same value as the \fBmessage\(hysubmission\(hyidentifier\fR supplied
to the originator of the
message when the message was submitted, and the \fBmessage\(hydelivery\(hyidentifier\fR
supplied to the recipient of the message when the message is delivered.
.PP
When a message is copied for routing to multiple recipients via
different MTAs, each copy of the message bears the \fBmessage\(hyidentifier\fR
of the original. The copies can be distinguished from one another by the
\fBoriginally\(hyspecified\(hyrecipient\(hynumber\fR and the corresponding
\fBresponsibility\fR arguments, which specify to which recipient(s) each
copy is to be
delivered.
.RT
.sp 1P
.LP
12.2.1.1.1.2\ \ \fIPer\(hydomain\(hybilateral\(hyinformation\fR
.sp 9p
.RT
.PP
This argument contains information intended for MDs which the
message will encounter as it is transferred through the MTS. It may be
generated by the originating\(hyMD of the message.
.PP
This argument may contain zero or more elements, each of which
comprises:
.RT
.LP
\(em
the \fBbilateral\(hyinformation\fR intended for an MD;
.LP
\(em
the \fBcountry\(hyname\fR , the \fBadministration\(hydomain\(hyname\fR and,
optionally, the \fBprivate\(hydomain\(hyidentifier\fR of the MD for which the
\fBbilateral\(hyinformation\fR is intended.
.sp 1P
.LP
12.2.1.1.1.3\ \ \fITrace\(hyinformation\fR
.sp 9p
.RT
.PP
This argument documents the actions taken on the message (or probe or report)
by each MD through which the message (or probe or report) passes as it
is transferred through the MTS (see\ \(sc\ 12.3.1). It shall be generated
by each MD through which the message (or probe or report) passes.
.RT
.sp 1P
.LP
12.2.1.1.1.4\ \ \fIInternal\(hytrace\(hyinformation\fR
.sp 9p
.RT
.PP
This argument documents the actions taken on the message (or probe or report)
by each MTA through which the message (or probe or report) passes as it
is transferred within an MD (see\ \(sc\ 12.3.1). It shall be generated
by each
MTA through which the message (or probe or report) passes within an MD.
.PP
This argument shall not be supplied by the invoker of the
message\(hytransfer abstract\(hyoperation when transferring a message to
another
MD, unless by bilateral agreement between MDs.
.RT
.sp 1P
.LP
12.2.1.1.1.5\ \ \fIOriginally\(hyspecified\(hyrecipient\(hynumber\fR
.sp 9p
.RT
.PP
This argument, combined with the \fBmessage\(hyidentifier\fR ,
unambiguously identifies the copy of the message delivered to each recipient.
It shall be generated by the originating\(hyMTA of the message. A different
value of this argument is specified for each recipient of the message.
.PP
The \fBoriginally\(hyspecified\(hyrecipient\(hynumber\fR is an integer
value in the range that begins with one and ends with the number of
originally\(hyspecified\(hyrecipients.
.bp
.RT
.ce
\fBH.T. [T29.411]\fR
.ce
TABLE\ 29/X.411
.ce
\fBMessage\(hytransfer arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRelaying arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hyidentifier M 12.2.1.1.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Per\(hydomain\(hybilateral\(hyinformation
T} C 12.2.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
Trace\(hyinformation M 12.2.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Internal\(hytrace\(hyinformation
T} C 12.2.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
DL\(hyexpansion\(hyhistory C \ 8.3.1.1.1.7\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIOriginator argument\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hyname M \ 8.2.1.1.1.1\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRecipient arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Recipient\(hyname M \ 8.2.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originally\(hyspecified\(hyrecipient\(hynumber
T} M 12.2.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
Responsibility M 12.2.1.1.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
DL\(hyexpansion\(hyprohibited C \ 8.2.1.1.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Disclosure\(hyof\(hyrecipients
T} C \ 8.2.1.1.1.7\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIRedirection arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Alternate\(hyrecipient\(hyallowed
T} C \ 8.2.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Recipient\(hyreassignment\(hyprohibited
T} C \ 8.2.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyrequested\(hyalternate\(hyrecipient
T} C \ 8.2.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
Intended\(hyrecipient\(hyname C \ 8.3.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
Redirection\(hyreason C \ 8.3.1.1.1.5\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIPriority argument\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Priority C \ 8.2.1.1.1.8\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIConversion arguments
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Implicit\(hyconversion\(hyprohibited
T} C \ 8.2.1.1.1.9\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Conversion\(hywith\(hyloss\(hyprohibited
T} C \ 8.2.1.1.1.10
.T&
lw(114p) | cw(30p) | cw(36p) .
Explicit\(hyconversion C \ 8.2.1.1.1.11
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIDelivery time arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
Deferred\(hydelivery\(hytime C 12.2.1.1.1.7\
.T&
lw(114p) | cw(30p) | cw(36p) .
Latest\(hydelivery\(hytime C \ 8.2.1.1.1.13
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIDelivery method argument\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Requested\(hydelivery\(hymethod
T} C \ 8.2.1.1.1.14
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIPhysical delivery arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyprohibited
T} C \ 8.2.1.1.1.15
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyaddress\(hyrequest
T} C \ 8.2.1.1.1.16
.T&
lw(114p) | cw(30p) | cw(36p) .
Physical\(hydelivery\(hymodes C \ 8.2.1.1.1.17
.T&
lw(114p) | cw(30p) | cw(36p) .
Registred\(hymail\(hytype C \ 8.2.1.1.1.18
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Recipient\(hynumber\(hyfor\(hyadvice
T} C \ 8.2.1.1.1.19
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyrendition\(hyattributes
T} C \ 8.2.1.1.1.20
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyreturn\(hyaddress
T} C \ 8.2.1.1.1.21
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIDelivery report request arguments
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyreport\(hyrequest
T} M \ 8.2.1.1.1.22
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originating\(hyMTA\(hyreport\(hyrequest
T} M 12.2.1.1.1.8\
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyreturn\(hyrequest C \ 8.2.1.1.1.23
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hydelivery\(hyreport\(hyrequest
T} C \ 8.2.1.1.1.24
.T&
lw(114p) | lw(30p) | lw(36p) .
\fISecurity arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hycertificate C \ 8.2.1.1.1.25
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hytoken C \ 8.2.1.1.1.26
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Content\(hyconfidentiality\(hyalgorithm\(hyidentifier
T} C \ 8.2.1.1.1.27
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyintegrity\(hycheck C \ 8.2.1.1.1.28
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Message\(hyorigin\(hyauthentication\(hycheck
T} C \ 8.2.1.1.1.29
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hysecurity\(hylabel C \ 8.2.1.1.1.30
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Proof\(hyof\(hydelivery\(hyrequest
T} C \ 8.2.1.1.1.32
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIContent arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Original\(hyencoded\(hyinformation\(hytypes
T} C \ 8.2.1.1.1.33
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hytype M \ 8.2.1.1.1.34
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyidentifier C \ 8.2.1.1.1.35
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hycorrelator C \ 8.2.1.1.1.36
.T&
lw(114p) | cw(30p) | cw(36p) .
Content M \ 8.2.1.1.1.37
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 29/X.411 [T29.411], p. 4\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
There is a one\(hyto\(hyone relationship between a particular
\fBoriginally\(hyspecified\(hyrecipient\(hynumber\fR value and a particular
\fBrecipient\(hyname\fR at the time of message\(hysubmission; it should
not be assumed that this is a
singular relationship at the time of message\(hydelivery. That is, an
\fBoriginally\(hyspecified\(hyrecipient\(hynumber\fR value can be used
to distinguish an
originally specified \fBrecipient\(hyname\fR , but not an actual recipient
that will
receive the message.
.RT
.sp 1P
.LP
12.2.1.1.1.6\ \ \fIResponsibility\fR
.sp 9p
.RT
.PP
This argument indicates whether the receiving\(hyMTA shall have the
responsibility to either deliver the message to a recipient or to transfer
it to another MTA for subsequent delivery to the recipient. It shall be
generated by the sending\(hyMTA. A different value of this argument may
be specified for
each recipient of the message.
.PP
This argument may have one of the following values: \fBresponsible\fR or
\fBnot\(hyresponsible\fR .
.RT
.sp 1P
.LP
12.2.1.1.1.7\ \ \fIDeferred\(hydelivery\(hytime\fR
.sp 9p
.RT
.PP
This argument is defined in\ \(sc\ 8.2.1.1.1.12. It may appear in a
message at a transfer\(hyport if there is a bilateral agreement that an
MTA other than the originating\(hyMTA of the message will defer the delivery
of the
message.
.RT
.sp 1P
.LP
12.2.1.1.1.8\ \ \fIOriginating\(hyMTA\(hyreport\(hyrequest\fR
.sp 9p
.RT
.PP
This argument indicates the kind of report requested by the
originating\(hyMTA. It shall be generated by the originating\(hyMTA of
the message. A different value of this argument may be specified for each
recipient of the
message.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBnon\(hydelivery\(hyreport\fR : a report is returned only in case of
non\(hydelivery, and it contains only the \fBlast\(hytrace\(hyinformation\fR
;
.LP
\(em
\fBreport\fR : a report is returned in case of delivery or
non\(hydelivery, and it contains only the \fBlast\(hytrace\(hyinformation\fR ;
.LP
\(em
\fBaudited\(hyreport\fR : a report is returned in case of delivery or
non\(hydelivery, and it contains all of the \fBtrace\(hyinformation\fR
.
.PP
The \fBoriginating\(hyMTA\(hyreport\(hyrequest\fR argument shall specify at
least the report level specified in the \fBoriginator\(hyreport\(hyrequest\fR
argument, where the increasing order or report levels is \fBno\(hyreport,
non\(hydelivery\(hyreport, report, audited\(hyreport\fR .
.sp 1P
.LP
12.2.1.1.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The message\(hytransfer abstract\(hyoperation does not return a
result.
.RT
.sp 1P
.LP
12.2.1.1.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
There are no abstract\(hyerrors that may disrupt the message\(hytransfer
abstract\(hyoperation.
.RT
.sp 1P
.LP
12.2.1.2\ \ \fIProbe\(hytransfer\fR
.sp 9p
.RT
.PP
The probe\(hytransfer abstract\(hyoperation enables an MTA to transfer
a probe to another MTA.
.RT
.sp 1P
.LP
12.2.1.2.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 30/X.411 lists the arguments of the probe\(hytransfer
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the paragraph in which the argument is defined.
.RT
.sp 1P
.LP
12.2.1.2.1.1\ \ \fIProbe\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains an \fBMTS\(hyidentifier\fR that distinguishes the
probe from all other message, probes and reports within the MTS. It shall
be
generated by the originating\(hyMTA of the probe, and shall have the same
value as the \fBprobe\(hysubmission\(hyidentifier\fR supplied to the originator
of the probe when the probe was submitted.
.RT
.sp 1P
.LP
12.2.1.2.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The probe\(hytransfer abstract\(hyoperation does not return a
result.
.RT
.sp 1P
.LP
12.2.1.2.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
There are no abstract\(hyerrors that may disrupt the probe\(hytransfer
abstract\(hyoperation.
.bp
.RT
.ce
\fBH.T. [T30.411]\fR
.ce
TABLE\ 30/X.411
.ce
\fBProbe\(hytransfer arguments
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRelaying arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Probe\(hyidentifier M 12.2.1.2.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Per\(hydomain\(hybilateral\(hyinformation
T} C 12.2.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
Trace\(hyinformation M 12.2.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Internal\(hytrace\(hyinformation
T} C 12.2.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
DL\(hyexpansion\(hyhistory C \ 8.3.1.1.1.7\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIOriginator argument\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hyname M \ 8.2.1.1.1.1\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRecipient arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Recipient\(hyname M \ 8.2.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originally\(hyspecified\(hyrecipient\(hynumber
T} M 12.2.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
Responsibility M 12.2.1.1.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
DL\(hyexpansion\(hyprohibited C \ 8.2.1.1.1.6\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIRedirection arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Alternate\(hyrecipient\(hyallowed
T} C \ 8.2.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Recipient\(hyreassignment\(hyprohibited
T} C \ 8.2.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyrequested\(hyalternate\(hyrecipient
T} C \ 8.2.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
Intended\(hyrecipient\(hyname C \ 8.3.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
Redirection\(hyreason C \ 8.3.1.1.1.5\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIConversion arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Implicit\(hyconversion\(hyprohibited
T} C \ 8.2.1.1.1.9\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Conversion\(hywith\(hyloss\(hyprohibited
T} C \ 8.2.1.1.1.10
.T&
lw(114p) | cw(30p) | cw(36p) .
Explicite\(hyconversion C \ 8.2.1.1.1.11
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIDelivery method argument\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
Request\(hydelivery\(hymethod C \ 8.2.1.1.1.14
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIPhysical delivery argument\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyrendition\(hyattributes
T} C \ 8.2.1.1.1.20
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIReport request arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyreport\(hyrequest
T} M \ 8.2.1.1.1.22
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originating\(hyMTA\(hyreport\(hyrequest
T} M 12.2.1.1.1.8\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fISecurity arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hycertificate C \ 8.2.1.1.1.25
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Probe\(hyorigin\(hyauthentication\(hycheck
T} C \ 8.2.1.2.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hysecurity\(hylabel C \ 8.2.1.1.1.30
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIContent arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Original\(hyencoded\(hyinformation\(hytypes
T} C \ 8.2.1.1.1.33
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hytype M \ 8.2.1.1.1.34
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyidentifier C \ 8.2.1.1.1.35
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hycorrelator C \ 8.2.1.1.1.36
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hylength C \ 8.2.1.2.1.2\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 30/X.411 [T30.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
12.2.1.3\ \ \fIReport\(hytransfer\fR
.sp 9p
.RT
.PP
The report\(hytransfer abstract\(hyoperation enables an MTA to transfer
a report to another MTA.
.RT
.sp 1P
.LP
12.2.1.3.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 31/X.411 lists the arguments of the report\(hytransfer
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the paragraph in which the argument is defined.
.RT
.sp 1P
.LP
12.2.1.3.1.1\ \ \fIReport\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains an \fBMTS\(hyidentifier\fR that distinguishes the
report from all other messages, probes and reports within the MTS. It shall
be generated by the originating\(hyMTA of the report.
.RT
.sp 1P
.LP
12.2.1.3.1.2\ \ \fIReport\(hydestination\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of the immediate destination
of the report. It shall be generated by the originating\(hyMTA of the report,
and subsequently modified by the DL expansion\(hypoints if any DLs had
been expanded to add recipients to the subject.
.PP
The originating\(hyMTA of the report shall set this argument to be the
\fBoriginator\(hyname\fR of the subject if the subject does not have a
\fBDL\(hyexpansion\(hyhistory\fR , or to the last \fBOR\(hyname\fR in the
\fBDL\(hyexpasion\(hyhistory\fR if this is present in the subject.
.PP
A DL expansion\(hypoint may replace its own \fBOR\(hyname\fR in this argument
by the \fBOR\(hyname\fR which immediately preceeds its own \fBOR\(hyname\fR
in the report's
\fBoriginator\(hyand\(hyDL\(hyexpansion\(hyhistory\fR , or some other \fBOR\(hyname\fR
according to
the reporting\(hypolicy of the DL.
.RT
.sp 1P
.LP
12.2.1.3.1.3\ \ \fISubject\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains the \fBmessage\(hyidentifier\fR (or
\fBprobe\(hyidentifier\fR ) of the subject (an \fBMTS\(hyidentifier\fR
). It shall be generated by the originating\(hyMTA of the subject.
.RT
.sp 1P
.LP
12.2.1.3.1.4\ \ \fISubject\(hyintermediate\(hytrace\(hyinformation\fR
.sp 9p
.RT
.PP
The argument contains the \fBtrace\(hyinformation\fR present in the
subject when it was transferred into the reporting\(hyMD. It shall be present
if, and only if, an audit\(hyand\(hyconfirmed report was requested by the
originating\(hyMTA of the subject. It may be generated by the reporting\(hyMTA.
.PP
\fINote\fR \ \(em\ The inclusion in the \fBsubject\(hyintermediate\(hytrace\(hyinformation\fR
of the \fBinternal\(hytrace\(hyinformation\fR present in the subject when
it was
transferred to the reporting\(hyMTA is for further study.
.RT
.sp 1P
.LP
12.2.1.3.1.5\ \ \fIArrival\(hytime\fR
.sp 9p
.RT
.PP
This argument contains the \fBtime\fR at which the subject entered the
MD making the report. It shall be generated by the originating\(hyMD of
the
report. A different value of this argument may be specified for each recipient
of the subject to which the report relates.
.RT
.sp 1P
.LP
12.2.1.3.1.6\ \ \fIAdditional\(hyinformation\fR
.sp 9p
.RT
.PP
The specification of the contents of this argument is by bilateral agreement
between MDs.
.RT
.sp 1P
.LP
12.2.1.3.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The report\(hytransfer abstract\(hyoperation does not return a
result.
.RT
.sp 1P
.LP
12.2.1.3.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
There are no abstract\(hyerrors that may disrupt the report\(hytransfer
abstract\(hyoperation.
.RT
.sp 1P
.LP
12.2.2
\fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
The transfer\(hyport has not abstract\(hyerrors.
.bp
.RT
.ce
\fBH.T. [T31.411]\fR
.ce
TABLE\ 31/X.411
.ce
\fBReport\(hytransfer arguments
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(144p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(144p) | lw(30p) | lw(36p) .
\fIRelaying arguments\fR
.T&
lw(144p) | cw(30p) | cw(36p) .
Report\(hyidentifier M 12.2.1.3.1.1\
.T&
lw(144p) | cw(30p) | cw(36p) .
Trace\(hyinformation M 12.2.1.1.1.3\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Internal\(hytrace\(hyinformation
T} C 12.2.1.1.1.4\
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fIReport destination argument\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
Report\(hydestination\(hyname M 12.2.1.3.1.2\
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fIReport request argument\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Originator\(hyreport\(hyrequest
T} M \ 8.2.1.1.1.22
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fISubject trace arguments\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
Subject\(hyidentifier M 12.2.1.3.1.3\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Originally\(hyspecified\(hyrecipient\(hynumber
T} M 12.2.1.1.1.5\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Subject\(hyintermediate\(hytrace\(hyinformation
T} C 12.2.1.3.1.4\
.T&
lw(144p) | cw(30p) | cw(36p) .
Arrival\(hytime M 12.2.1.3.1.5\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Originator\(hyand\(hyDL\(hyexpansion\(hyhistory
T} C \ 8.3.1.2.1.3\
.T&
lw(144p) | cw(30p) | cw(36p) .
Reporting\(hyDL\(hyname C \ 8.3.1.2.1.4\
.T&
lw(144p) | lw(30p) | lw(36p) .
\fIConversion argument\fR
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Converted\(hyencoded\(hyinformation\(hytypes
T} C \ 8.3.1.2.1.5\
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fISupplementary information arguments\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
Supplementary\(hyinformation C \ 8.3.1.2.1.6\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyaddress
T} C \ 8.3.1.2.1.7\
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fISubject redirection arguments\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
Actual\(hyrecipient\(hyname M \ 8.3.1.2.1.2\
.T&
lw(144p) | cw(30p) | cw(36p) .
Intended\(hyrecipient\(hyname C \ 8.3.1.1.1.4\
.T&
lw(144p) | cw(30p) | cw(36p) .
Redirection\(hyreason C \ 8.3.1.1.1.5\
.T&
lw(144p) | lw(30p) | lw(36p) .
\fIContent arguments\fR
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Original\(hyencoded\(hyinformation\(hytypes
T} C \ 8.2.1.1.1.33
.T&
lw(144p) | cw(30p) | cw(36p) .
Content\(hytype C \ 8.2.1.1.1.34
.T&
lw(144p) | cw(30p) | cw(36p) .
Content\(hyidentifier C \ 8.2.1.1.1.35
.T&
lw(144p) | cw(30p) | cw(36p) .
Content\(hycorrelator C \ 8.2.1.1.1.36
.T&
lw(144p) | cw(30p) | cw(36p) .
Returned\(hycontent C \ 8.3.1.2.1.14
.T&
lw(144p) | lw(30p) | lw(36p) .
\fIDelivery arguments\fR
.T&
lw(144p) | cw(30p) | cw(36p) .
Message\(hydelivery\(hytime C \ 8.2.1.2.1.8\
.T&
lw(144p) | cw(30p) | cw(36p) .
Type\(hyof\(hyMTS\(hyuser C \ 8.3.1.2.1.9\
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fINon\(hydelivery arguments\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Non\(hydelivery\(hyreason\(hycode
T} C \ 8.3.1.2.1.10
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Non\(hydelivery\(hydiagnostic\(hycode
T} C \ 8.3.1.2.1.11
.T&
lw(144p) | lw(30p) | lw(36p) .
\fISecurity arguments\fR
.T&
lw(144p) | cw(30p) | cw(36p) .
Recipient\(hycertificate C \ 8.3.1.1.2.1\
.T&
lw(144p) | cw(30p) | cw(36p) .
Proof\(hyof\(hydelivery C \ 8.3.1.1.2.2\
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Reporting\(hyMTA\(hycertificate
T} C \ 8.3.1.2.1.12
.T&
lw(144p) | cw(30p) | cw(36p) .
T{
Report\(hyorigin\(hyauthentication\(hycheck
T} C \ 8.3.1.2.1.13
.T&
lw(144p) | cw(30p) | cw(36p) .
Message\(hysecurity\(hylabel C \ 8.2.1.1.1.30
.T&
lw(144p) | lw(30p) | lw(36p) .
T{
\fIAdditional information argument\fR
T}
.T&
lw(144p) | cw(30p) | cw(36p) .
Additional\(hyinformation C 12.2.1.3.1.6\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 31/X.411 [T31.411], p. \fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
12.3
\fICommon parameter types\fR
.sp 9p
.RT
.PP
This paragraph defines a number of common parameter types of the
MTA abstract service.
.RT
.sp 1P
.LP
12.3.1
\fITrace\(hyinformation and internal\(hytrace\(hyinformation\fR
.sp 9p
.RT
.PP
\fBTrace\(hyinformation\fR documents the actions taken on a message, probe
or report by each MD through which it passes as it is transferred through
the MTS.
.PP
\fBInternal\(hytrace\(hyinformation\fR documents the action taken on a
message, probe or report by each TMA through which it passes as it is transferred
through an MD. \fBInternal\(hytrace\(hyinformation\fR shall be removed
from a message,
probe or report before it is transferred out of an MD, unless by bilateral
agreement between MDs.
.PP
\fBTrace\(hyinformation\fR (or \fBinternal\(hytrace\(hyinformation\fR )
comprises a
sequence of \fBtrace\(hyinformation\(hyelements\fR (or \fBinternal\(hytrace\(hyinformation\(hyelements\fR
).
The first \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) is that supplied by
the originating\(hyMD
(or \(hyMTA) of the message, probe or report. The second
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
) is that supplied by the next MD (or MTA) encountered by the message,
probe or report, and so on. Each MD (or MTA) adds its \fBtrace\(hyinformation\(hyelement\fR
(or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) to the end of the existing
sequence.
\fBTrace\(hyinformation\fR is added by the first MTA encountered by the
message, probe or report in each MD it passes through.
.PP
Each \fBtrace\(hyinformation\(hyelement\fR includes the
\fBglobal\(hydomain\(hyidentifier\fR of the MD supplying the
\fBtrace\(hy
\fBinformation\(hyelement\fR .
.PP
Each \fBinternal\(hytrace\(hyinformation\(hyelement\fR includes the \fBMTA\(hyname\fR
of the MTA supplying the \fBinternal\(hytrace\(hyinformation\(hyelement\fR
and the
\fBglobal\(hydomain\(hyidentifier\fR of the MD to which the MTA belongs.
.PP
Each \fBtrace\(hyinformation\(hyelement\fR (or \fBin
ternal\(hytrace\(hyinformation\(hyelement\fR ) includes the \fBarrival\(hytime\fR
at which the
message, probe or report entered the MD (or MTA). In the case of the
originating\(hyMD (or \(hyMTA) of the message, probe or report, the \fBarrival\(hytime\fR
is the time of message\(hysubmission, probe\(hysubmission or report generation,
respectively.
.PP
Each \fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
) specifies the \fBrouting\(hyaction\fR
the MD (or
MTA) supplying the \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) took with respect to
the message, probe or report. \fBRelayed\fR is the normal \fBrouting\(hyaction\fR
of transferring the
message, probe or report to another MD (or MTA). \fBRerouted\fR indicates
that an attempt had previously been made to route the message, probe or
report to an
\fBattempted\(hydomain\fR (or \fBattempted\(hyMTA\fR ); the \fBglobal\(hydomain\(hyidentifier\fR
of the \fBattempted\(hydomain\fR is included in the \fBtrace\(hyinformation\(hyelement\fR
; if the
rerouting attempt was to another MTA within the same MD, then the MTA\(hyname
of the \fBattempted\(hyMTA\fR is included in the \fBinternal\(hytrace\(hyinformation\(hyelement\fR
;
if the rerouting attempt was to another MD, then the \fBglobal\(hydomain\(hyidentifier\fR
of the \fBattempted\(hydomain\fR is included in the
\fBinternal\(hytrace\(hyinformation\(hyelement\fR instead of an \fBMTA\(hyname\fR
.
.PP
Each \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) also specifies any
\fBadditional\(hyactions\fR the MD (or MTA) supplying the \fBtrace\(hyinformation\(hyelement\fR
(or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) took with respect to
the message, probe or report. Indications of any such \fBadditional\(hyactions\fR
which appear in the
\fBinternal\(hytrace\(hy
\fBinformation\(hyelements\fR during a traversal of an MD shall
also be
reflected in the corresponding \fBtrace\(hyinformation\(hyelement(s)\fR
for the traversal of the MD.
.PP
If the deferred\(hydelivery caused the MD (or MTA) supplying the
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
) to hold the message for a period of time, the \fBdeferred\(hytime\fR
when it started to
process the message for delivery or transfer is also included in the
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
). This
parameter is not present in \fBtrace\(hyinformation\(hyelements\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelements\fR ) on probes and reports.
.PP
If the MD (or MTA) supplying the \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) subjects a message
to conversion, the
\fBconverted\(hyencoded\(hyinformation\(hytypes\fR resulting from the conversion
is also
included in the \fBtrace\(hyinformation\(hyelement\fR (or \fB
internal\(hytrace\(hyinformation\(hyelement\fR ). For a probe, an MD that
would have
converted the subject\(hymessage indicates the \fBencoded\(hyinformation\(hytypes\fR
the
subject\(hymessage would contain after conversion in its
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
). This
parameter is not present in \fBtrace\(hyinformation\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) on reports.
.PP
If the MD (or MTA) redirects a message or a probe (for any, but not
necessarily all, of a message's or probe's recipients), \fBredirected\fR is
indicated in the \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ). This parameter is
not present in
\fBtrace\(hyinformation\fR (or \fBinternal\(hytrace\(hyinformation\fR )
on reports.
.bp
.PP
If the MD (or MTA) expands a DL of a message or a probe,
\fBdl\(hyoperation\fR is indicated in \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ). If the MD (or MTA) is a DL
expasion\(hypoint and replaces its own \fBOR\(hyname\fR in the \fBreport\(hydestination\(hyname\fR
of a report with another \fBOR\(hyname\fR (see \(sc\ 12.2.1.3.1.2), \fBdl\(hyoperation\fR
is indicated in the \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) of the report.
.PP
Loop detection and suppression is done by an MD (or MTA) when it
receives a message, probe or report from another MD (or MTA). Messages,
probes and reports may legitimately re\(hyenter an MD (or MTA) for several
reasons
(\fBrerouted\fR , etc) and consequently a message, probe or report may
have several disjoint \fBtrace\(hyinformation\(hyelements\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelements\fR ) from the same MD (or
MTA). Each time a message, probe or report is transferred through an MD
(or MTA) the generation of \fBtrace\(hyinformation\(hyelements\fR (or \fBinternal\(hytrace\(hy\fR
\fBinformation\(hyelements\fR ) is performed as follows:
.RT
.LP
i)
one \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) is added, marked as
\fBrelayed\fR ;
.LP
ii)
if a rerouting attempt is to occur, then the
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hyinformation\(hyelement\fR
) added
in\ i) is modified to \fBrerouted\fR (and the number of \fBtrace\(hyinformation\(hyelement\fR
(or \fBinternal\(hytrace\(hyinformation\(hyelements\fR ) added by the MD
(or MTA) for this
traversal of the MD (or MTA) remains at one);
.LP
iii)
if subsequent attempts to reroute occur, then a new
\fBtrace\(hyinformation\(hyelement\fR (or \fBinternal\(hytrace\(hy\fR
\fBinformation\(hyelement\fR ) is added (marked as \fBrerouted\fR ) to
reflect each new rerouting attempt.
.PP
Several rerouting attempts to the same MD (or MTA) may occur.
.PP
Each \fBtrace\(hyinformation\(hyelement\fR (or
\fBinternal\(hytrace\(hyinformation\(hyelement\fR ) added by an MD (or
MTA) may contain
indications of \fBadditional\(hyactions\fR performed by the MD (or MTA)
on the message or probe (i.e.,\ \fBdeferred\(hy time\fR (not present in
\fBtrace\(hyinformation\fR (or
\fBinternal\(hytrace\(hyinformation\fR ) on probes),
\fBconverted\(hyencoded\(hy\fR \fBinformation\(hytypes\fR , \fBredirected\fR
or \fBdl\(hyoperation\fR ).
.RT
.sp 2P
.LP
\fB13\fR \fBMessage transfer agent abstract syntax definition\fR
.sp 1P
.RT
.PP
The abstract\(hysyntax of the MTA abstract service is defined in
Figure\ 4/X.411.
.PP
The abstract\(hysyntax of the MTA abstract service is defined using the
abstract syntax notation (ASN.1) defined in Recommendation\ X.208, and
the
absract service definition conventions defined in
Recommendation\ X.407.
.PP
The abstract\(hysyntax definition of the MTA abstract service has the
following major parts:
.RT
.LP
\(em
\fIPrologue\fR : declaration of the exports from, and imports to, the
MTA abstract service module (Figure 4/X.411, Part\ 1).
.LP
\(em
\fIMTS refinement, objects and ports\fR : refinement of the MTS
object, and definitions of the MTA object and the transfer\(hyport
(Figure\ 4/X.411, Part\ 2).
.LP
\(em
\fIMTA\(hybind and MTA\(hyunbind\fR : definitions of the MTA\(hybind and
MTA\(hyunbind used to establish and release associations between MTAs
(Figure\ 4/X.411, Part\ 3).
.LP
\(em
\fITransfer ports\fR : definitions of the transfer\(hyport
abstract\(hyoperations: message\(hytransfer, probe\(hytransfer and report\(hytransfer
(Figure\ 4/X.411, Part\ 4).
.LP
\(em
\fIMessage transfer envelope\fR : definition of the
message\(hytransfer\(hyenvelope (Figure\ 4/X.411, Parts\ 5 and\ 6).
.LP
\(em
\fIProbe transfer envelope\fR : definition of the
probe\(hytransfer\(hyenvelope (Figure\ 4/X.411, Part\ 7).
.LP
\(em
\fIReport transfer envelope and content\fR : definitions of the
report\(hytransfer\(hyenvelope and report\(hytransfer\(hycontent (Figure\
4/X.411, Part\ 8).
.LP
\(em
\fIEnvelope and report content fields\fR : definitions of envelope and
report content fields (Figure\ 4/X.411, Parts\ 9 and\ 10).
.LP
\(em
\fIExtension fields\fR : definitions of extension\(hyfields
(Figure\ 4/X.411, Parts\ 11 and 12).
.LP
\(em
\fICommon parameters types\fR : definitions of common parameter
types (Figure\ 4/X.411, Part\ 13).
.PP
\fINote\fR \ \(em\ The module implies a number of changes to the P1 protocol
defined in Recommendation\ X.411 (1984). These changes are highlighted
by means of
underlining
.
.PP
Each \fBextension\(hyfield\fR defined in Figure\ 4/X.411 (Parts\ 12 and\ 13)
carries with it an indication of its \fBcriticality\fR for submission,
transfer and delivery. The criticality mechanism is described in\ \(sc\
9.1, and the procedures related to \fBextension\(hyfields\fR and their
\fBcriticality\fR indications are further defined in\ \(sc\ 14.
.bp
.RT
.LP
MTAAbstractService { joint\(hyiso\(hyccitt mhs\(hymotis(6) mts(3) modules(0)
mta\(hyabstract\(hyservice(2) }
.LP
DEFINITIONS IMPLICIT TAGS ::=
.LP
BEGIN
.LP
.sp 2
\(hy\(hy\|\fIPrologue\fR
.LP
\(hy\(hy\|\fIExports everything\fR
.LP
.sp 2
IMPORTS
.LP
\(hy\(hy\|\fIAbstract service macros\fR
.LP
REFINE, OBJECT, PORT, ABSTRACT\(hyBIND, ABSTRACT\(hyUNBIND,
ABSTRACT\(hyOPERATION
.LP
FROM AbstractServiceNotation { joint\(hyiso\(hyccitt mhs\(hymotis(6)
asdc(2) modules(0)
.LP
notation(1) }
.LP
\(hy\(hy\|\fIMTS abstract service parameters\fR
.LP
mTS, submission, delivery, administration, InitiatorCredentials,
SecurityContext,
.LP
ResponderCredentials, OriginalEncodedInformationTypes,
ContentTypes, ContentIdentifier,
.LP
Priority, PerMessageIndicators, DeferredDeliveryTime, CountryName,
AdministrationDomainName,
.LP
PrivateDomainIdentifier, ExplicitConversion, ContentLength,
ConvertedEncodedInformationTypes,
.LP
ReportType, SupplementaryInformation,
EXTENSION, EXTENSIONS, recipient\(hyreassignment\(hyprohibited,
.LP
dl\(hyexpansion\(hyprohibited, conversion\(hywith\(hyloss\(hyprohibited,
latest\(hydelivery\(hytime,
.LP
requested\(hydelivery\(hymethod, physical\(hyforwarding\(hyprohibited,
physical\(hyforwarding\(hyaddress\(hyrequest,
.LP
physical\(hydelivery\(hymodes, registered\(hymail\(hytype, recipient\(hynumber\(hyfor\(hyadvice,
physical\(hyrendition\(hyattributes,
.LP
originator\(hyreturn\(hyaddress, physical\(hydelivery\(hyreport\(hyrequest,
originator\(hycertificate, message\(hytoken,
.LP
content\(hyconfidentiality\(hyalgorithm\(hyidentifier, content\(hyintegrity\(hycheck,
message\(hyorigin\(hyauthentication\(hycheck,
.LP
message\(hysecurity\(hylabel, proof\(hyof\(hydelivery\(hyrequest, content\(hycorrelator,
probe\(hyorigin\(hyauthentication\(hycheck,
.LP
redirection\(hyhistory, dl\(hyexpansion\(hyhistory, originator\(hyand\(hydl\(hyexpansion\(hyhistory,
reporting\(hydl\(hyname,
.LP
physical\(hyforwarding\(hyaddress, recipient\(hycertificate, proof\(hyof\(hydelivery,
reporting\(hyMTA\(hycertificate,
.LP
report\(hyorigin\(hyauthentication\(hycheck, Content, MTSIdentifier,
GlobalDomainIdentifier, MTAName, Time,
.LP
ORAddressAndOptionalDirectoryName
.LP
FROM MTSAbstractService { joint\(hyiso\(hyccitt mhs\(hymotis(6) mts(3)
modules(0)
.LP
mts\(hyabstract\(hyservice(1) }
.LP
\(hy\(hy\|\fIObject identifiers\fR
.LP
id\(hyot\(hymta, id\(hypt\(hytransfer
.LP
FROM MTSObjectIdentifiers { joint\(hyiso\(hyccitt mhs\(hymotis(6)
mts(3) modules(0)
.LP
object\(hyidentifiers(0) }
.LP
\(hy\(hy\|\fIUpper bounds\fR
.LP
ub\(hybit\(hyoptions, ub\(hydl\(hyexpansions, ub\(hyinteger\(hyoptions,
ub\(hyrecipients, ub\(hyredirections, ub\(hytransfers
.LP
FROM MTSUpperBounds { joint\(hyiso\(hyccitt mhs\(hymotis(6) mts(3)
modules(0)
.LP
upper\(hybounds(3) };
.ce 1000
FIGURE\ 4/X.411\ (Part\ 1 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\|\fIMTS refinement\fR
.LP
MTSRefinement ::= REFINE mTS AS
.LP
mTA RECURRING
.LP
submission
[S]
VISIBLE
.LP
delivery
[S]
VISIBLE
.LP
administration
[S]
VISIBLE
.LP
transfer
PAIRED WITH mTA
.LP
.sp 2
\(hy\(hy\|\fIObjects\fR
.LP
mTA OBJECT
.LP
PORTS { submission [S], delivery [S], administration [S],
transfer }
.LP
::= id\(hyot\(hymta
.LP
.sp 2
.LP
\(hy\(hy\|\fIPorts\fR
.LP
transfer PORT
.LP
ABSTRACT OPERATIONS { MessageTransfer, ProbeTransfer,
ReportTransfer }
.LP
::= id\(hypt\(hytransfer
.ce 1000
FIGURE\ 4/X.411\ (Part\ 2 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.sp 8
.LP
\(hy\(hy\|\fIMTA\(hybind and MTA\(hyunbind\fR
.LP
MTABind ::= ABSTRACT\(hyBIND
.LP
TO { transfer }
.LP
BIND
.LP
ARGUMENT CHOICE {
.LP
NULL,
\(hy\(hy\|if no authentication is required
.LP
[1] SET {
\(hy\(hy\|if authentication is required
.LP
initiator\(hyname [0] MTAName,
.LP
initiator\(hycredentials [1] InitiatorCredentials,
.LP
security\(hycontext [2] SecurityContext OPTIONAL
} }
.LP
RESULT CHOICE {
.LP
NULL,
\(hy\(hy\|if no authentication is required
.LP
[1] SET {
\(hy\(hy\|if authentication is required
.LP
responder\(hyname [0] MTAName,
.LP
responder\(hycredentials [1] ResponderCredentials
} }
.LP
BIND\(hyERROR INTEGER {
.LP
busy (0),
.LP
authentication\(hyerror (2),
.LP
unacceptable\(hydialogue\(hymode (3)
.LP
unacceptable\(hysecurity\(hycontext (4)
}
(0\|.\|.\|ub\(hyinteger\(hyoptions)
.LP
MTAUnbind ::= ABSTRACT\(hyUNBIND
.LP
FROM { transfer }
.ce 1000
FIGURE\ 4/X.411\ (Part\ 3 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\|\fITransfer port\fR
.LP
MessageTransfer ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT Message
.LP
ProbeTransfer ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT Probe
.LP
ReportTransfer ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT Report
.LP
Message ::= SEQUENCE {
.LP
envelope MessageTransferEnvelope,
.LP
content Content }
.LP
Probe ::= ProbeTransferEnvelope
.LP
Report ::= SEQUENCE {
.LP
envelope ReportTransferEnvelope,
.LP
content ReportTransferContent }
.ce 1000
FIGURE\ 4/X.411\ (Part\ 4 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.sp 8
.LP
\(hy\(hy\|\fIMessage transfer envelope\fR
.LP
MessageTransferEnvelope ::= SET {
.LP
COMPONENTS OF PerMessageTransferFields,
.LP
per\(hyrecipient\(hyfields [2] SEQUENCE
SIZE (1\|.\|.\|ub\(hyrecipients)
OF
.LP
PerRecipientMessageTransferFields }
.LP
PerMessageTransferFields ::= SET {
.LP
message\(hyidentifier MessageIdentifier,
.LP
originator\(hyname OriginatorName,
.LP
original\(hyencoded\(hyinformation\(hytypes OriginalEncodedInformationTypes
OPTIONAL,
.LP
content\(hytype ContentType,
.LP
content\(hyidentifier ContentIdentifier OPTIONAL,
.LP
priority Priority DEFAULT normal,
.LP
per\(hymessage\(hyindicators PerMessageIndicators DEFAULT {\|},
.LP
deferred\(hydelivery\(hytime [0] DeferredDeliveryTime OPTIONAL,
.LP
per\(hydomain\(hybilateral\(hyinformation [1] SEQUENCE OF
PerDomainBilateralInformation OPTIONAL,
.LP
trace\(hyinformation TraceInformation,
.LP
extension [3] EXTENSIONS CHOSEN FROM {
.LP
recipient\(hyreassignment\(hyprohibited,
.LP
dl\(hyexpansion\(hyprohibited,
.LP
conversion\(hywith\(hyloss\(hyprohibited,
.LP
latest\(hydelivery\(hytime,
.LP
originator\(hyreturn\(hyaddress,
.LP
originator\(hycertificate,
.LP
content\(hyconfidentiality\(hyalgorithm\(hyidentifier,
.LP
message\(hyorigin\(hyauthentication\(hycheck,
.LP
message\(hysecurity\(hylabel,
.LP
content\(hycorrelator,
.LP
dl\(hyexpansion\(hyhistory,
.LP
internal\(hytrace\(hyinformation} DEFAULT {\|}
}
.ce 1000
FIGURE\ 4/X.411\ (Part\ 5 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
PerRecipientMessageTransferFields ::= SET {
.LP
recipient\(hyname RecipientName,
.LP
originally\(hyspecified\(hyrecipient\(hynumber [0]
OriginallySpecifiedRecipientNumber,
.LP
per\(hyrecipient\(hyindicators [1] PerRecipientIndicators,
.LP
explicit\(hyconversion [2] ExplicitConversion OPTIONAL,
.LP
extension [3] EXTENSIONS CHOSEN FROM {
.LP
originator\(hyrequested\(hyalternate\(hyrecipient,
.LP
requested\(hydelivery\(hymethod,
.LP
physical\(hyforwarding\(hyprohibited,
.LP
physical\(hyforwarding\(hyaddress\(hyrequest,
.LP
physical\(hydelivery\(hymodes,
.LP
registered\(hymail\(hytype,
.LP
recipient\(hynumber\(hyfor\(hyadvice,
.LP
physical\(hyrendition\(hyattributes,
.LP
physical\(hydelivery\(hyreport\(hyrequest,
.LP
message\(hytoken,
.LP
content\(hyintegrity\(hycheck,
.LP
proof\(hyof\(hydelivery\(hyrequest,
.LP
redirection\(hyhistory } DEFAULT {\|}
}
.ce 1000
FIGURE\ 4/X.411\ (Part\ 6 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.sp 5
.LP
\(hy\(hy\|\fIProbe transfer envelope\fR
.LP
ProbeTransferEnvelope ::= SET {
.LP
COMPONENT OF PerProbeTransferFields,
.LP
per\(hyrecipient\(hyfield [2] SEQUENCE
SIZE (1\|.\|.\|ub\(hyrecipient)
OF PerRecipientProbeTransferFields }
.LP
PerProbeTransferFields ::= SET {
.LP
probe\(hyidentifier ProbeIdentifier,
.LP
originator\(hyname OriginatorName,
.LP
original\(hyencoded\(hyinformation\(hytypes OriginalEncodedInformationTypes
OPTIONAL,
.LP
content\(hytype\(hyContentType,
.LP
content\(hyidentifier ContentIdentifier OPTIONAL,
.LP
content\(hylength [0] ContentLength OPTIONAL,
.LP
per\(hymessage\(hyindicators PerMessageIndicators DEFAULT {\|},
.LP
per\(hydomain\(hybilateral\(hyinformation [1] SEQUENCE
SIZE (1\|.\|.\|ub\(hytransfers)
OF
.LP
PerDomainBilateralInformation OPTIONAL,
.LP
trace\(hyinformation TraceInformation,
.LP
extensions [3] EXTENSIONS CHOSEN FROM {
.LP
recipient\(hyreassignment\(hyprohibited,
.LP
dl\(hyexpansion\(hyprohibited,
.LP
conversion\(hywith\(hyloss\(hyprohibited,
.LP
originator\(hycertificate,
.LP
message\(hysecurity\(hylabel,
.LP
content\(hycorrelator,
.LP
probe\(hyorigin\(hyauthentication\(hycheck,
.LP
dl\(hyexpansion\(hyhistory,
.LP
internal\(hytrace\(hyinformation} DEFAULT {\|}
}
.LP
PerRecipientProbeTransferFields ::= SET {
.LP
recipient\(hyname RecipientName,
.LP
originally\(hyspecified\(hyrecipient\(hynumber [0]
OriginallySpecifiedRecipientNumber,
.LP
per\(hyrecipient\(hyindicators [1] PerRecipientIndicators,
.LP
explicit\(hyconversion [2] ExplicitConversion OPTIONAL,
.LP
extensions [3] EXTENSIONS CHOSEN FROM {
.LP
originator\(hyrequested\(hyalternate\(hyrecipient,
.LP
requested\(hydelivery\(hymethod,
.LP
physical\(hyrendition\(hyattributes,
.LP
redirection\(hyhistory } DEFAULT {\|}
}
.ce 1000
FIGURE\ 4/X.411\ (Part\ 7 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\|\fIReport transfer envelope\fR
.LP
ReportTransferEnvelope ::= SET {
.LP
report\(hyidentifier ReportIdentifier,
.LP
report\(hydestination\(hyname ReportDestinationName,
.LP
trace\(hyinformation TraceInformation,
.LP
extensions [1] EXTENSIONS CHOSEN FROM {
.LP
message\(hysecurity\(hylabel,
.LP
originator\(hyand\(hyDL\(hyexpansion\(hyhistory,
.LP
reporting\(hyDL\(hyname,
.LP
reporting\(hyMTA\(hycertificate,
.LP
report\(hyorigin\(hyauthentication\(hycheck,
.LP
internal\(hytrace\(hyinformation} DEFAULT {\|}
}
.LP
.sp 2
.LP
\(hy\(hy\|\fIReport transfer content\fR
.LP
ReportTransferContent ::= SET {
.LP
COMPONENT OF PerReportTransferFields,
.LP
per\(hyrecipient\(hyfields [0] SEQUENCE
SIZE (1\|.\|.\|ub\(hyrecipients)
OF
.LP
PerRecipientReportTransferFields }
.LP
PerReportTransferFields ::= SET {
.LP
subject\(hyidentifier SubjectIdentifier,
.LP
subject\(hyintermediate\(hytrace\(hyinformation
SubjectIntermediateTraceInformation OPTIONAL,
.LP
original\(hyencoded\(hyinformation\(hytypes
OriginalEncodedInformationTypes OPTIONAL,
.LP
content\(hytype ContentType OPTIONAL,
.LP
content\(hyidentifier ContentIdentifier OPTIONAL,
.LP
returned\(hycontent [1] Content OPTIONAL,
.LP
additional\(hyinformation [2] AdditionalInformation OPTIONAL,
.LP
extensions [3] EXTENSIONS CHOSEN FROM {
.LP
content\(hycorrelator } DEFAULT {\|}
}
.LP
PerRecipientReportTransferFields ::= SET {
.LP
actual\(hyrecipient\(hyname [0] ActualRecipientName,
.LP
originally\(hyspecified\(hyrecipient\(hynumber [1]
OriginallySpecifiedRecipientNumber,
.LP
per\(hyrecipient\(hyindicator [2] PerRecipientIndicators,
.LP
last\(hytrace\(hyinformation [3] LastTraceInformation,
.LP
originally\(hyintended\(hyrecipient\(hyname [4]
OriginallyIntendedRecipientName OPTIONAL,
.LP
supplementary\(hyinformation [5] SupplementaryInformation OPTIONAL,
.LP
extensions [6] EXTENSIONS CHOSEN FROM {
.LP
redirection\(hyhistory,
.LP
physical\(hyforwarding\(hyaddress,
.LP
recipient\(hycertificate,
.LP
proof\(hyof\(hydelivery } DEFAULT {\|}
}
.ce 1000
FIGURE\ 4/X.411\ (Part\ 8 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\|\fIEnvelope and report content fields\fR
.LP
MessageIdentifier ::= MTSIdentifier
.LP
OriginatorName ::= ORAddressAndOptionalDirectoryName
.LP
PerDomainBilateralInformation ::= SEQUENCE {
.LP
country\(hyname CountryName,
.LP
CHOICE {
.LP
administration\(hydomain\(hyname AdministrationDomainName,
.LP
SEQUENCE {
.LP
administration\(hydomain\(hyname [0] AdministrationDomainName,
.LP
private\(hydomain\(hyidentifier [1] PrivateDomainIdentifier
OPTIONAL
} },
.LP
bilateral\(hyinformation BilateralInformation }
.LP
BilateralInformation ::= ANY\ \ \ \(hy\(hymaximum ub\(hybilateral\(hyinfo
octets including all encoding
.LP
RecipientName ::= ORAddressAndOptionalDirectoryName
.LP
OriginallySpecifiedRecipientNumber ::= INTEGER
(SIZE (1\|.\|.\|ub\(hyrecipients))
.LP
PerRecipientIndicators ::= BIT STRING {
.LP
responsibility (0),
.LP
\(hy\(hy\|reponsible 'one', not\(hyresponsible 'zero'
.LP
originating\(hyMTA\(hyreport (1),
.LP
originating\(hyMTA\(hynon\(hydelivery\(hyreport (2),
.LP
\(hy\(hy\|either originating\(hyMTA\(hyreport, or
originating\(hyMTA\(hynon\(hydelivery\(hyreport, or both, shall be 'one':
.LP
\(hy\(hy\|originating\(hyMTA\(hyreport bit 'one' requests a 'report';
.LP
\(hy\(hy\|originating\(hyMTA\(hynon\(hydelivery\(hyreport bit 'one' requests a
'non\(hydelivery\(hyreport';
.LP
\(hy\(hy\|both bits 'one' requests and 'audited\(hyreport';
.LP
\(hy\(hy\|bits 0\(hy2 'don't care' for Report Transfer Content
.LP
originator\(hyreport (3),
.LP
originator\(hynon\(hydelivery\(hyreport (4),
.LP
\(hy\(hy\|at most one bit shall be 'one':
.LP
\(hy\(hy\|originator\(hyreport bit 'one' requests a 'report';
.LP
\(hy\(hy\|originator\(hynon\(hydelivery\(hyreport bit 'one' requests a
'non\(hydelivery\(hyreport';
.LP
\(hy\(hy\|both bits 'zero' requests 'no\(hyreport'
.LP
reserved\(hy5 (5),
.LP
reserved\(hy6 (6),
.LP
reserved\(hy7 (7),
.LP
\(hy\(hy\|reserved\(hybits 5\(hy7 shall be 'zero' \(hy\(hy\|}
(SIZE (8\|.\|.\|ub\(hybit\(hyoptions))
.LP
ProbeIdentifier ::= MTSIdentifier
.ce 1000
FIGURE\ 4/X.411 (Part\ 9 fo\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.sp 8
.LP
ReportIdentifier ::= MTSIdentifier
.LP
ReportDestinationName ::= ORAddressAndOptionalDirectoryName
.LP
SubjectIdentifier ::= MessageOrProbeIdentifier
.LP
MessageOrProbeIdentifier ::= MTSIdentifier
.LP
SubjectIntermediateTraceInformation ::= TraceInformation
.LP
AdditionalInformation ::= ANY\ \ \ \(hy\(hy\|maximum ub\(hyadditional\(hyinfo
octets including all enconding
.LP
ActualRecipientName ::= ORAddressAndOptionalDirectoryName
.LP
LastTraceInformation ::= SET {
.LP
arrival\(hytime [0] ArrivalTime,
.LP
converted\(hyencoded\(hyinformation\(hytype
ConvertedEncodedInformationTypes OPTIONAL,
.LP
report\(hytype [1] ReporType }
.LP
OriginallyIntendedRecipientName ::= ORAddressAndOptionalDirectoryName
.ce 1000
FIGURE\ 4/X.411\ (Part\ 10 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\|\fIExtension fields\fR
.LP
originator\(hyrequested\(hyalternate\(hyrecipient EXTENSION
.LP
OriginatorRequestedAlternateRecipient
.LP
::= 2
.LP
OriginatorRequestedAlternateRecipient ::= ORAddressAndOptionalDirectoryName
.LP
internal\(hytrace\(hyinformation EXTENSION
.LP
InternalTraceInformation
.LP
::= 38
.ce 1000
FIGURE\ 4/X.411\ (Part\ 11 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.sp 3
.LP
InternalTraceInformation ::= SEQUENCE SIZE (1\|.\|.\|ub\(hytransfers) OF
InternalTraceInformationElement
.LP
InternalTraceInformationElement ::= SEQUENCE {
.LP
global\(hydomain\(hyidentifier GlobalDomainIdentifier,
.LP
mta\(hyname MTAName,
.LP
mta\(hysupplied\(hyinformation MTASuppliedInformation }
.LP
MTASuppliedInformation ::= SET {
.LP
arrival\(hytime [0] ArrivalTime,
.LP
routing\(hyaction [2] RoutingAction,
.LP
attempted CHOICE {
.LP
mta MTAName,
.LP
domain GlobalDomainIdentifier } OPTIONAL,
.LP
\(hy\(hy\|\fIadditional\(hyactions\fR \(hy\(hy\|COMPONENTS OF
InternalAdditionalActions }
.LP
InternalAdditionalActions ::= AdditionalActions
.ce 1000
FIGURE\ 4/X.411\ (Part\ 12 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
\(hy\(hy\|\fICommon parameter types\fR
.LP
TraceInformation ::= [APPLICATION 9] SEQUENCE
(SIZE (1\|.\|.\|ub\(hytransfers)
OF TraceInformationElement
.LP
TraceInformationElement ::= SEQUENCE {
.LP
global\(hydomain\(hyidentifier GlobalDomainIdentifier,
.LP
domain\(hysupplied\(hyinformation DomainSuppliedInformation }
.LP
DomainSuppliedInformation ::= SET {
.LP
arrival\(hytime [0] ArrivalTime,
.LP
routing\(hyaction [2] RoutingAction,
.LP
attempted\(hydomain GlobalDomainIdentifier OPTIONAL,
.LP
\(hy\(hy\|\fIadditional\(hyactions\fR \(hy\(hy\|COMPONENT OF AdditionalActions
}
.LP
AdditionalActions ::= SET {
.LP
deferred\(hytime [1] DeferredTime OPTIONAL,
.LP
converted\(hyencoded\(hyinformation\(hytypes
ConvertedEncodedInformationTypes OPTIONAL,
.LP
other\(hyactions [3] OtherActions DEFAULT {\|}
}
.LP
RoutingAction ::= ENUMERATED {
.LP
relayed (0),
.LP
rerouted (1) }
.LP
DeferredTime ::= Time
.LP
ArrivalTime ::= Time
.LP
OtherActions ::= BIT STRING {
.LP
redirected (0),
.LP
dl\(hyoperation (1) } (SIZE (0\|.\|.\|ub\(hybit\(hyoptions))
.LP
END\ \(hy\(hy\|\fIof MTA abstract service\fR
.ce 1000
FIGURE\ 4/X.411\ (Part\ 13 of\ 13)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTA abstract service\fR
.ce 0
.sp 1P
.LP
.bp